Batch scheduling

ABSTRACT

There is provided a method to schedule execution of a plurality of batch jobs by a computer system. The method includes: reading one or more constraints that constrain the execution of the plurality of batch jobs by the computer system and a current load on the computer system; grouping the plurality of batch jobs into at least one run frequency that includes at least one batch job; setting the at least one run frequency to a first run frequency; computing a load generated by each batch job in the first run frequency on the computer system based on each batch job&#39;s start time; and determining an optimized start time for each batch job in the first run frequency that meets the one or more constraints and that distributes each batch job&#39;s load on the computer system using each batch job&#39;s computed load and the current load.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Utility application Ser. No. 11/645,947, dated Dec. 27, 2006, which is hereby incorporated by reference in its entirety.

TECHNICAL FIELD

This disclosure relates generally to data processing systems. More particularly, example embodiments are directed to batch scheduling in data processing systems.

BACKGROUND

In general, batch jobs are back office processes executed by a computer system off-line (e.g., not in real time) and non-interactively (e.g., without user interaction). Because batch jobs are typically compute-intensive, they are generally queued or accumulated during peaks hours when computing resources are unavailable or constrained by real-time activities, and are they then executed during non-peak or idle hours when computing resources are available or less constrained. A batch job is generally stored in an input file—often called a batch file, command file or shell script—which is executed by the computer system. The execution of the input file may produce a number of actions as diverse as updating databases, reconciliation of financial transactions, sending emails to users or producing one or more output files to be used by another batch job or a business.

In general, batch jobs run regularly (e.g. daily, weekly, monthly, etcetera). Many batch jobs access databases to get information needed to perform their function. The execution priority order and frequency of queued or accumulated batch jobs is generally managed by a batch scheduler. Generally, an organization or enterprise may execute its own batch jobs using a standalone batch processing computer system or batch server pool that includes plural servers to process the input files (e.g., batch jobs). However, the organization or enterprise that has finite computing resources may wish to outsource the execution of some or all of its batch jobs, or parts thereof, to an organization that has available computing resources to fulfill this need. Therefore, scheduling performed by the batch scheduler may be constrained by a number of factors, including the following factors.

A first factor may be the available capacity in a batch server pool that processes the batch jobs. The available number of servers in the batch server pool may be a limiting factor in executing a large number and/or time-consuming batch jobs.

A second factor may be the service level agreements (SLAs) between the batch job owner and the computing resource owner (e.g., third-party system). SLAs normally specify the frequency of execution of the batch jobs, as well as the start and completion deadlines of such execution. If SLAs are missed, there may be financial impact to the batch job owner and/or customer impact (e.g., batch jobs that are not completed in time).

A third factor may be the availability, load and capacity of the third-party system (e.g., databases, mail servers, and the like) that are needed to execute or complete the processing of batch jobs. It is often the case that the third-party system is shared by other functions (e.g., other departments, other types of load such as real-time traffic, and the like) and is not readily available, e.g., it may only be used at certain times and/or not all their capacity is available.

As a result of the third constraint factor above, it is often simpler to add capacity to the batch server pool than to make capacity and load changes to the third-party system impacted by the batch job. In these cases, batch job scheduling is actually constrained by the third-party.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings in which:

FIG. 1 is a block diagram illustrating an example batch system;

FIG. 2 is a flowchart illustrating an example scheduling and optimization method performed by batch scheduler of FIG. 1;

FIG. 3 is an example table illustrating a service level agreement for plural batch jobs to be executed by the example third party system of FIG. 1.

FIG. 4 is an example table illustrating performance metrics collected for the plural batch jobs of FIG. 3 executed on the example third party system of FIG. 1;

FIG. 5A is an example table illustrating a number of operations per hour measured for the third party system of FIG. 1;

FIG. 5B is an example table illustrating a maximum operations per hour that the third party system of FIG. 1 can perform.

FIG. 6 is an example table that illustrates plural batch jobs of FIG. 3 regularized and grouped by job frequencies in the batch scheduler of FIG. 1;

FIG. 7 is an example display of batch scheduler of FIG. 1 with an initial schedule of regularized batch jobs of FIG. 6 before optimization of the initial schedule;

FIG. 8 is an example display illustrating the initial schedule of FIG. 7 optimized by the batch scheduler of FIG. 1; and

FIG. 9 is a block diagram illustrating an example computer system within which a set of instructions, for causing the computer system to perform any one or more of the methodologies disclosed in FIGS. 1-8, may be executed.

DETAILED DESCRIPTION

An example system, method and machine-readable medium for generating an optimized batch schedule are described. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of example embodiments. It will be evident, however, to one skilled in the art that an example embodiment may be practiced without these specific details.

Example embodiments described herein include a system, method, and machine-readable medium for generating an optimized batch schedule that accounts for service level agreements (i.e., “SLAs”) and constraints of a third-party system that processes scheduled batch jobs.

FIG. 1 is a block diagram illustrating an example batch system 100 that accounts for service level agreements (SLAs) and constraints of a third-party system 130 in scheduling execution of a plurality of batch jobs by the third party system 130. The example system 100 includes batch job parameters and constraints 104, a batch scheduler 110, a batch processing system 122 and a third party system 130. For brevity and clarity, example embodiments are described in relation to a third-party system 130. It should be noted, however, that system 100 is easily scalable and plural third-party systems 130 may be provided in different implementations to execute a number of batch schedules of batch jobs. The various elements of the system 100 described herein may be interconnected via any conventional mechanisms, including local area network (LAN), wide area network (WAN), the Internet, and combinations thereof.

Further with reference to FIG. 1, batch job parameters and constraints 104 include databases 106 and 108, which store batch job parameters and constraints utilized by the batch scheduler 110 to generate an optimized schedule of batch jobs to be executed by the third party system 130. More specifically, the business requirements database 106 maintains a service level agreement (SLA) with the third-party system 130 for processing or execution of batch jobs using the third-party system 130. A example SLA will be described below with reference to FIG. 3. At this point, it is sufficient to mention that the SLA includes one or more batch jobs that are to be executed using the third-party system 130 and the SLA further provides a run frequency (e.g., hourly, daily, weekly, etc.), a start time after which the batch job should start and an end time before which the batch job should terminate for the batch job. The SLA may be stored in the business requirement database 106 via manual input or downloaded from a storage device using computer system 102. It is noted that the foregoing batch job parameters and constraints may be stored and maintained in greater or fewer databases, and may be stored in tables, flat files and the like. Furthermore, the foregoing batch job parameters and constraints may also be maintained directly by the batch scheduler 110 in one or more databases, tables, or files.

Still further with reference to FIG. 1, the performance and capacity database 108 maintains batch job parameters and constraints associated with the third-party system 130. For example, the performance and capacity database 108 may maintain batch job metrics, such as a number of operations performed by a batch job and an average duration of execution of the batch job on the third party system 130. The performance and capacity database 108 may further maintain information related to the third party system 130, such as a maximum allowable load (e.g., maximum number of operation per hour) that the third party system 130 may perform per hour and an expected load (e.g., number of operations per hour) that the third party system 130 is expected to perform per hour in a twenty four hour period. The performance and capacity database 108 may also maintain scheduler configuration parameters, such as a busy minute multiplier, an approximation parameter and initial hour parameter, as will be described in greater detail herein. The batch job parameters and constraints associated with the third-party system 130 are downloaded or otherwise provided by a batch server pool 124 of the batch processing system 122, which in turn obtains this information from the third party system 130. The foregoing parameters and constraints will be described in greater detail below with reference to FIGS. 2-4.

Yet further with reference to FIG. 1, databases 106 and 108 are operatively and communicatively interconnected to the batch scheduler 110, which reads the SLA (including batch jobs to be executed) as well as the related batch job parameters and constraints associated with the third-party system 130 from databases 106, 108, and generates an optimized batch schedule of the batch jobs that accounts for the SLA as well as the parameters and constraints of the third-party systems 130, which is to process or otherwise execute the scheduled batch jobs. More specifically, the batch scheduler 110 includes input module 112 that reads the foregoing parameters and constraints from databases 106, 108 into the batch scheduler 110. Furthermore, the batch scheduler 110 includes a frequency regularization module 113, which regularizes and groups batch jobs with irregular run frequencies (e.g., hourly, daily, weekly, monthly, etc.) to respective batch jobs with regular run frequencies. For example, if a batch is to be executed a number of times daily, a number of instances of the batch job are defined for each run of that batch job in the day. The batch scheduler 110 further includes a load initialization module 114, which determines or computes the hourly load (e.g., operations per hour) on the third party system that is generated by non-batch tasks (e.g., web traffic, daemons, etc.) on the third party system 130 as a function of that batch job's start time and end time. Yet further, the batch scheduler 110 includes time initialization module 115, which initializes the start time of each batch job. More specifically, the time initialization module 115 sets the initial start time for each batch job to an arbitrary value h0, which may or may not meet the SLA, parameters and constraints. The initial value of the start time influences the optimized batch schedule. For some selections of start times, the optimization described herein may not be able to determine a schedule that meets the constraints, while for other selections such a schedule may be determined. Thus, setting the initial start time value h0 in the least busy hour of the third party system 130 tends to ensure convergence to a schedule that meets the SLA, parameters and constraints. The batch scheduler 110 also includes a start time determination module 116 that computes an optimized start time for each batch job that meets the SLA, parameters and constraints, and which minimizes the load generated by the batch job on the third party system 130. Still further, the batch scheduler 110 includes a schedule generation module 118 that generates an optimized batch schedule. The batch scheduler 110 also includes a load update module 120 that updates a load produced by the optimized batch job schedule on the third party system 130. More specifically, the load values determined or computed by the load initialization module 114 are updated with the load derived form the batch jobs scheduled by the schedule generation module 118.

In addition with reference to FIG. 1, the batch scheduler 110 is operatively and communicatively interconnected to the batch processing system 122. The batch processing system 122 includes a batch server pool 124, which is bidirectionally interconnected to a batch input/output file database 128 and which is further bidirectionally interconnected to the third-party system 130. Also, the batch server pool 124 further provides the parameters and constraints of the third-party system 130 described herein to the performance and capacity database 108. The batch server pool 124 includes a batch job controller 126, which controls one or more batch servers 125 in executing batch jobs scheduled by the batch scheduler 110 to be executed by the batch processing system 122. The batch job controller 126 may be a software or hardware controller, whose role is to launch batch jobs in each of the batch servers 125 in the batch server pool 124. The batch job controller 126 may be standalone or incorporated into a batch server 125. The batch job controller 126 launches batch jobs in any of the batch servers 125 in the batch server pool 124 according to the batch schedule computed in 118. A batch process while running in one of the batch servers 124 may read data from and write data to the batch input/output database 128. Furthermore, some batch jobs executed on the batch processing system 122 may require access to the third party system 130 during their execution. The third party system 130 party system 130.

FIG. 2 is a flowchart illustrating an example scheduling and optimization method 200 performed by batch scheduler 110 that accounts for service level agreements and constraints of a third-party system 130 in scheduling the execution of plural batch jobs by the third-party 130 system illustrated of FIG. 1. The flowchart start at operation 202. At operation 204, the service level agreement (SLA), configuration values, parameters and constraints for each of a plurality of batch jobs are read by the batch scheduler 110 from databases 106, 108. These values may be arranged and stored in tables as illustrated in FIGS. 3-5 and described below with reference therewith. At this point the different constraints, metrics and configuration values will be described generally. More specifically, for each batch job in the SLA, the following batch job parameters are read from the business requirement database 106: 1) a run frequency for the batch job (e.g., hourly, daily, weekly, etc.); 2) start time after which the batch job should start in accordance with the SLA (e.g., Start_SLA(b)); and 3) end time before which the batch job should end in accordance with the SLA (e.g., End_SLA(b)). These parameters are described in more detail in reference to FIG. 3 below. Batch job parameters or metrics for each batch job in the SLA on the third party system 130 that are read from the performance and capacity database 108 include: 1) total operations generated by the batch job on the third party system 130 (e.g., Total_Batch_Ops (b,s)); and 2) the average job duration of the batch job (e.g., Dur(b)). These parameters are described in more detail in reference to FIG. 4 below. Third party system parameters that are read from the performance and capacity database 108 include: 1) an expected load (e.g., number of total operations during each hour on the third party system 130 denoted by Total_RT_Ops (h,s)); and 2) a maximum load (e.g., maximum number of operations the third party system can support denoted by Max_Ops(s)). These parameters are described in more detail in reference to FIGS. 5A-5B below. Lastly, configuration parameters for scheduling that are read from the performance and capacity database 108 include: 1) busy minute multiplier (e.g., BZ_Min); 2) an approximation parameter (e.g., parameter “a”); and 3) and initial hour parameter (e.g., parameter “h0”).

Further with reference to FIG. 2, at operation 206 a list of batch jobs with irregular run frequencies is identified. More specifically, batch jobs whose run frequencies are not expressed as daily run frequencies in the SLA (FIG. 3) are identified. This may include batch jobs that run a number of times daily, and those that run weekly, monthly, or at some other time periods. At operation 208, the identified batch jobs that have irregular run frequencies are regularized to batch jobs that have regular run frequencies. The regularization is performed as follows.

First, if batch job b must start to run at a specified time, it is set to start at this specified time and is removed from the list of batch jobs to schedule. Thus, if the batch job must start to run in hour h, the expected load per minute in hour h on the third party system s 130,

${{{RT\_ Ops}\left( {h,s} \right)} = \frac{{TOTAL\_ RT}{\_ OPS}\left( {h,s} \right)}{60}},$

is incremented by the quantity

${BZ\_ Min}\; {\frac{{Total\_ Batch}{\_ Ops}\left( {b,s} \right)}{{Dur}\mspace{11mu} (b)}.}$

The former calculation takes the expected number of total operations during each hour on the third party system 130 (e.g., Total_RT_Ops(h,s)) and divides that number by 60 minutes to obtain a number of expected operations (load) per minute performed on the third party system 130. The latter calculation takes the total operations generated by the batch job on the third party system 130 (e.g., Total_Batch_Ops(b,s)), divides that number by the average job duration of the batch job (e.g., Dur(b)) and multiples by the busy minute multiplier (e.g., BZ_Min)), adding to that result the expected operations per minute performed on the third party system 130 (e.g., RT_Ops(h,s)). The foregoing adds the load generated by the batch job that must run at a specified time to the overall load of the third party system 130. This is done because there is nothing to schedule for a batch job that must run at a specified time. More specifically, SLA and the parameters and constraints imposed determine when this batch job must run. The multiplier (e.g., BZ_Min)) may be set to a value of 2 or 3, or another value. The multiplier captures a worst case scenario for total number of operations (load) performed during the job duration of the batch job b on system s 130,

${BZ\_ Min}\; {\frac{{Total\_ Batch}{\_ Ops}\left( {b,s} \right)}{{Dur}\mspace{11mu} (b)}.}$

For example, if in one hour (e.g., Dur(b)) there are 6000 batch operations by batch job b on third party system s 130 (e.g., Total_Batch_Ops(b,s)), there would be on average 100 batch operations per minute. However, since this is the average the number of batch operations per minute may be higher or lower. To protect against a worst case scenario in which the batch operations per minute are higher than the average, a multiplier (e.g., 2, 3, or another multiplier) may be used to increase the number of batch operations per minute to 200 or 300 batch operation per minute. Thus, the BZ_Min multiplier transforms the number of operations in the average minute to the number of operations expected during a busiest minute.

Yet further with reference to FIG. 2, operation 208 continues as follows. Second, if a particular batch job b has an incomplete run frequency (e.g., weekdays vs. daily), and if that batch job b runs n times (e.g. n=5 in the weekdays vs. daily case), then n batch jobs are defined as follows, b1, b2, . . . , bn with the same average job duration of the batch job (e.g., Dur(b)) and same SLA (FIG. 3) as the particular batch job b, but each defined batch job running at the next lower frequency schedule (e.g., in the case of weekdays, b1 runs weekly on Mondays, . . . , b5 runs weekly on Fridays . . . ). Third, if a particular batch job b has an over-filled run frequency (e.g., runs twice daily), and if batch job b runs n times (e.g. n=2 in the twice a day case), define n batch jobs, b1, b2, . . . , bn with same average job duration of the batch job (e.g., Dur(b)) as batch job b, with each defined batch job running at the same frequency schedule as the particular batch job b (e.g., defined batch jobs b1 and b2 each run daily with Start_SLA and End_SLA associated with batch job b with over-filled frequency). Thus, operation 208 regularizes batch jobs with irregular run frequencies to batch jobs with regular frequencies (e.g., daily, weekly, monthly).

Still further with reference to FIG. 2, at operation 210, the regularized batch jobs are grouped by the associated run frequencies (e.g., hourly, daily, weekly, monthly, yearly, etc.). For example, the batch jobs may be grouped from the highest frequency (e.g., daily) through to the next highest (e.g., weekly), the next highest (e.g., monthly) and finally the lowest frequency (e.g., yearly). For example, the grouping may be accomplished by grouping daily batch jobs (those that run once or multiple times daily) into group (D), grouping weekly batch jobs into group (W), grouping monthly batch jobs into group (M) and grouping yearly batch jobs into group (Y). At operation 212, the highest frequency not yet scheduled is set. For example, the setting of the frequency may be accomplished by setting a variable S equal to D (e.g., daily). Operations 214 through 226 are then performed for each batch job in the group S of batch jobs identified above. Thus, at operation 214, the start time and the end time are initialized for each batch job b in group S. That is, the start time for batch job b is initialized as Start(b)=h0 and the end time for batch job b is initialized as End(b)=h0+Dur(b). The start time may be initialized to any time. At operation 216, each batch job b operations per hour h (load) on third party system s 130 is computed as the following smooth function of its start time (e.g., Start(b) and end time (e.g., End(b)):

${{Batch\_ Ops}\; \left( {b,h,s} \right)} = {\frac{{Total\_ Batch}{\_ Ops}\mspace{11mu} \left( {b,s} \right)}{\pi \; {Dur}\mspace{11mu} (b)}\left( {{{Tan}^{- 1}\left( {a\left( {h - {{Start}\mspace{14mu} (b)}} \right)} \right)} - {{Tan}^{- 1}\left( {a\left( {h - {{End}\mspace{14mu} (b)}} \right)} \right)}} \right)}$

Batch_Ops(b, h, s), the load generated by batch jobs is a step function. It is noted that any other methodology that provides a close approximation to the Batch_Ops(b, h, s) may also be used.

Further yet with reference to FIG. 2, at operation 218, an optimized start time is computed for each batch job b in the group S that meets constraints and distributes each batch job's load on the third party system s 130 that minimizes the overall load on the third party system s 130. More specifically, for each batch job b in group S, a value of Start(b) that maximizes the following formula is determined:

${\sum\limits_{s}^{\;}\; {\sum\limits_{h}^{\;}\; \left( {1 - {{Bz\_ Min}\; \frac{{{RT\_ Ops}\left( {h,s} \right)} + {\sum\limits_{b\; \in \; S}\; {{Batch\_ Ops}\; \left( {b,h,s} \right)}}}{{Max\_ Ops}\; (s)}}} \right)^{2}}},$

subject to the following constraints: Start_SLA(b)≦Start (b)<24 for all batch jobs b in group S; 0≦Start (b)+Dur(b)≦End_SLA(b) for all batch jobs b in group S; and

${{BZ\_ Min}\left( {{{RT\_ Ops}\left( {h,s} \right)} + {\sum\limits_{b\; \in \; S}^{\;}\; {{Batch\_ Ops}\left( {b,h,s} \right)}}} \right)} \leq {{Max\_ Ops}\; (s)}$

for third party

system s and hour h. The first two constraints ensure that the batch job b satisfies SLA requirements, starting after Start_SLA(b) and ending before End_SLA(b), respectively. The last constraint ensures that the batch jobs in group S will not put excessive load on the third party system s 130.

Additionally with reference to FIG. 2, the previous step 218 computed optimized start times (Start(b)) for all batch jobs in group S subject to the constraints identified therewith. Thereafter, at operation 220 a schedule is generated for all batch jobs in group S. It is noted that the batch jobs in group S in the generated schedule fulfil the foregoing constraints. More specifically, that the start time (Start(b)) of each batch job is after the time specified in the SLA (Start_SLA(b)), the end time (Start (b)+Dur(b)) is before the time specified in the SLA (End_SLA(b)) for that batch job, and that batch jobs in group S will not put excessive load on third party system 130 (e.g., ≧max_Ops(s)). This completes the scheduling/optimization of highest frequency schedule (e.g., daily schedule D). At operation 222, it is determined whether there another frequency to schedule (e.g., weekly, monthly, yearly, etc.). If there is no other frequency to schedule, the flowchart 200 terminates at operation 228. Alternatively, the flowchart 200 continues at operation 224, in which a load placed by the batch jobs of groups S on the third party system s 130 is calculated and the total or overall load on the third party system s 130 (e.g., RT_Ops(h,s)) is updated to reflect the load placed by the batch jobs in group S as follows:

${{RT\_ Ops}\left( {h,s} \right)} = {{{RT\_ Ops}\left( {h,s} \right)} + {{BZ\_ Min}\; {\frac{\sum\limits_{b\mspace{11mu} \in \mspace{11mu} S}^{\;}\; {{Total\_ Batch}{\_ Ops}\left( {b,s} \right)}}{{Dur}\mspace{11mu} (b)}.}}}$

At operation 226, the next highest frequency not yet scheduled is set (e.g., weekly). More specifically, the variable S is set to group W (e.g., weekly) Thereafter the flowchart 200 continues at operation 214, and performs operations 214-226 for the next highest frequency (e.g., weekly). The operations 214-226 described are performed for each frequency not yet scheduled unit all frequencies of batch jobs have been scheduled.

FIG. 3 is an example table 300 illustrating a service level agreement (SLA) for plural batch jobs to be executed by the example third party system 130 of FIG. 1. The SLA table 300 may be in the business requirement database 106. Form time to time the SLA table 300 may be updated via computer system 102, as described above in reference to FIG. 1. The SLA table includes one or more job name that identify respective batch jobs (e.g., batch job A, B, C, and the like) to be executed by the third party system 130. It is noted that the batch job name may be a descriptive alphanumeric string and the like. For each batch job, the following fields are specified: 1) frequency of execution; 2) number of time of execution; 2) start time (Start_SLA) after which the batch job is to begin; and 3) end time (End_SLA) before which the batch job is to end. For example, bath job A has a daily frequency with only one execution. Batch job B has a daily frequency with two executions (e.g., 10, 20), while batch job C has hourly executions (e.g., at 0, 4, 8, 12, 14, 16 and 20).

FIG. 4 is an example table 400 illustrating performance metrics collected for the plural batch jobs of FIG. 3 executed on the example third party system 130 of FIG. 1. More specifically, the particular batch jobs (e.g., batch jobs A, B and C) of FIG. 3 are executed on the third party system 130 and the metrics of their execution (e.g., operations performed) on the third party system 130 is collected. Table 400 illustrates each of the batch job's metrics, including total operations performed by each batch job and the average job duration of each batch job on the third party system 130 of FIG. 1. The operations may be measured differently depending on what type of operations are performed. In the case of a database, as a batch job will perform on the database multiple types of transactions such (e.g., selects, updates, and the like), these transactions can all be measured in “buffer gets”, which is a unit one would use to measure the impact on the database. For instance, assume that a select takes 10 buffer gets and an updated takes 50 buffer gets. Thus, a batch job that performs 200 selects and 50 updates will perform (200*10)+(50*50)=4500 batch operations (e.g., buffer gets) on a database. As noted in reference to FIG. 1, these metrics may be colleted by the batch server pool 124 from the third party system 130 and stored to the performance and capacity database 108 for later retrieval and usage by the batch scheduler 110.

FIG. 5A is an example table 500 a illustrating a number of operations per hour measured for the third party system 130 of FIG. 1. FIG. 5B is an example table 500 b illustrating a maximum operations per hour that the third party system of FIG. 1 can perform. For example, in reference to tables 5A-5B, in the zero hour the third party system 130 has been measured as performing 68,629 operations from a maximum or a total of 120,000 operations. Thus, the headroom (HR) of available capacity on the third party system 130 for the zero hour is approximately 42.81% (e.g., (120,000−68,629)/120,000)), while the headroom HR) available for the twenty-first hour is approximately 2.26% (e.g., (120,000−117,293)/120,000)). The load on the third party system 130 for the zero hour and the twenty-first hour is 57.19% and 97.74%, respectively. Therefore, what is illustrated in tables 5A-5B is the load and available capacity in terms of operations per hour on the third party system 130.

FIG. 6 is an example table 600 that illustrates plural batch jobs of FIG. 3 regularized and grouped by job frequencies in the batch scheduler 110 of FIG. 1. Example table 600 illustrates the input of FIGS. 3-5 consolidated and processed by the batch schedule 110 to a form usable in the scheduling and optimization performed by the batch scheduler 110, described in reference to FIGS. 1 and 2 above. More specifically, the batch jobs have been regularized and grouped as described in reference to operations 208 and 210 with reference to FIG. 2 above. Each batch job is assigned a sequential job id. It is noted that the SLA start and SLA end are expressed in minutes rather than hours. For example with reference to batch job A (e.g., job id=1), a start SLA of 180 minutes means the batch job needs to start after 3:00 AM and an end SLA of 630 means the batch job need to end before 10:30 AM.

FIG. 7 is an example display 700 of batch scheduler of FIG. 1 with an initial schedule of regularized batch jobs of FIG. 6 before optimization of the initial schedule. The schedule generation module 118 of FIG. 1 may generate display 700. As illustrated in the display 700, the start time and end time of each batch has been initialized, as described in operation 214 with reference to FIG. 2 above. For example, the start time of the first job A (e.g., job id=1) is initialized to 740 minutes (e.g., 12:40 PM) and the end time of this job is initialized to 825 minutes (e.g., 1:45 PM), which is the start time 740 (e.g., 12:40 PM) plus the average duration 65 (e.g., 1:05 hr) from table 600 of FIG. 6. As can easily be appreciated, the start time of 740 (e.g., 12:40 PM) is after the SLA start of 180 minutes (e.g., 3:00 PM), and therefore meets the SLA start time. However, the end time of 825 minutes (e.g., 1:45 PM) for the first batch job (e.g., job id=1) is after the SLA end time of 630 minutes (e.g., 10:30 AM), and therefore violates the SLA end time. In table 700, shaded cells show start time or end time violations of respective SLA start or SLA end times of the batch jobs identified by their batch ID numbers. The AVG HR cell (e.g., 27%) is a value that represents the left over or free capacity in the third party system 130 that would result after execution the non-optimized schedule illustrated in table 700 of FIG. 7. More specifically, the AVG HR is a delta between the maximum operations (load) allowed in the third party system 103 (FIG. 5B) and the load that results from the foregoing non-optimized schedule of batch jobs.

FIG. 8 is an example display 800 illustrating the initial schedule of FIG. 7 optimized by the batch scheduler 110 of FIG. 1. The schedule generation module 118 of FIG. 1 may generate display 800. More specifically, steps 216-226 of FIG. 2 have been preformed as described above on the batch jobs illustrated in FIG. 7 to generate the optimized schedule illustrated in FIG. 8. The schedule generation module 118 of FIG. 1 may generate display 800. As can easily appreciated, there are no more violations (e.g., no shaded cells) of the respective SLA start or SLA end times of the batch jobs identified by their batch ID numbers. It is also noted that that the AVG HR increased from 27% to 32%, representing an increase of free capacity in the third party system 130 after executing the optimized schedule illustrated in table 800 of FIG. 8. The average headroom (e.g., AVG HR) may be calculated by operation 224 of FIG. 2 via load update module 120 of FIG. 1.

In reference to FIGS. 1-8, the optimization can be extended to include a file size of a batch job. More specifically, the number of actions a batch job generates may be proportional to a number of lines in an input file or the size of the input file for that batch job. If File_Size(b) is an input file size (e.g., in lines) for a batch job b, it can be determined what maximum input file size Max_File_Size(b) a schedule may support by replacing Batch_Ops(b, h, s) described above in reference to FIG. 2 with the following:

${{Batch\_ Ops}\left( {b,h,s} \right)} = {{Bz\_ Min}\; \frac{{Batch\_ Ops}\left( {b,s} \right)}{{File\_ Size}(b)}{\frac{{Max\_ File}{\_ Size}\; (b)}{{Dur}\mspace{11mu} (b)}.}}$

In the foregoing function it can be determined when a constraint breaks as the maximum file size increases from its current value. More specifically, input file size may be used as a proxy for the number of batch operations (load) that a batch job will generate. It is to be noted that the batch job duration to execute the input file will increase as a result of the increase of file size. The new duration can be estimated as

${Dur}\mspace{11mu} (b)\; {\frac{{Max\_ File}{\_ size}\mspace{11mu} (b)}{{File\_ Size}\mspace{11mu} (b)}.}$

Further with reference to FIGS. 1-8, when batch jobs have different scheduling frequencies as described herein, the scheduling problem can still be resolved within this framework described in reference to FIGS. 1-8. For instance, if a job must run hourly, the load generated by this job,

${{BZ\_ Min}\mspace{11mu} \frac{{Total\_ Batch}{\_ Ops}\left( {b,s} \right)}{{Dur}\mspace{11mu} (b)}},$

can be added to all RT_Ops(h, s) values. For example, if batch job A runs four times a day, four batch jobs like job A may be defined that run once a day with different SLAs that ensure the four daily runs. However, if a batch job that must run at a specific given time is scheduled at this time, the load generated is given by

${BZ\_ Min}\mspace{11mu} \frac{{Total\_ Batch}{\_ Ops}\left( {b,s} \right)}{{Dur}\mspace{11mu} (b)}$

is added to RT_Ops(h, s). Batch jobs that run several times a week but not daily can be treated as follows. Assume for example that a batch job runs on weekdays only. Therefore this situation can be treated as having 5 different weekly batch jobs, each running a different day of the week and each of the batch jobs gets scheduled when scheduling optimization is performed for each day. Weekly batch jobs that do not have a day constraint (e.g., can run on any day of the week but must run once a week) get scheduled after the schedules for daily batch jobs have been set by incorporating the load generated by daily jobs into the RT_OPS(h, s) value for every day. The same applies for monthly jobs.

FIG. 9 is a block diagram illustrating an example machine in the example form of a computer system 900 within which a set of instructions, for causing the computer system to perform any one or more of the methodologies disclosed in FIGS. 1-8, may be executed. In alternative embodiments, the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

The example computer system 900 includes a processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 904 and a static memory 906, which communicate with each other via a bus 908. The computer system 900 may further include a video display unit 910 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 900 also includes an alphanumeric input device 912 (e.g., a keyboard), a user interface (UI) navigation device 914 (e.g., a mouse), a disk drive unit 916, a signal generation device 918 (e.g., a speaker) and a network interface device 920.

The disk drive unit 916 includes a machine-readable medium 922 on which is stored one or more sets of instructions and data structures (e.g., software 924) embodying or utilized by any one or more of the methodologies or functions described herein. The software 924 may also reside, completely or at least partially, within the main memory 904 and/or within the processor 902 during execution thereof by the computer system 900, the main memory 904 and the processor 92 also constituting machine-readable media.

The software 924 may further be transmitted or received over a network 926 via the network interface device 920 utilizing any one of a number of well-known transfer protocols (e.g., HTTP).

While the machine-readable medium 922 is shown in an example embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “machine-readable medium” shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such a set of instructions. The term “machine-readable medium” shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals.

Although an embodiment of the present invention has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader spirit and scope of the invention. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof, show by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

Such embodiments of the inventive subject matter may be referred to herein, individually and/or collectively, by the term “invention” merely for convenience and without intending to voluntarily limit the scope of this application to any single invention or inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description

In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of an embodiment of the present invention. It will be evident, however, to one skilled in the art that the present invention may be practiced without these specific details. 

1. A method to schedule execution of a plurality of batch jobs by a computer system, the method comprising: reading one or more constraints that constrain the execution of the plurality of batch jobs by the computer system, including constraints from a service level agreement, and a current load on the computer system; grouping the plurality of batch jobs into at least one run frequency that includes at least one batch job; setting the at least one run frequency to a first run frequency; computing a load generated by each batch job in the first run frequency on the computer system based on each batch job's start time to protect against a worst case in which a number of batch operations in such given time period is higher than an average number of batch operations expected during the busiest of such given time period; and determining an optimized start time for each batch job in the first run frequency that meets the one or more constraints and that distributes each batch job's load on the computer system using each batch job's computed load and the current load, the one or more constraints including at least one constraint of the service level agreement.
 2. The method of claim 1, further comprising initializing each batch job's start time to a preset value.
 3. The method of claim 1, further comprising regularizing at least one batch job with an irregular run frequency from the plurality of batch jobs to a batch job with a regular frequency.
 4. The method of claim 1, further comprising generating a batch job schedule for the first run frequency.
 5. The method of claim 1, updating the current load on the computer system with loads of each batch job in the first frequency.
 6. The method of claim 5, further comprising: setting the at least one run frequency to a second run frequency; computing a load generated by each batch job in the second run frequency on the computer system based on each batch job's start time; and determining an optimized start time for each batch job in the second run frequency that meets the one or more constraints and that distributes each batch job's load on the computer system using each batch job's computed load and the updated current load for the first run frequency.
 7. A system to schedule execution of a plurality of batch jobs by a third party computer system, the system comprising: an input module adapted to read one or more constraints that constrain the execution of the plurality of batch jobs by the third party computer system, including constraints from a service level agreement, and a current load on the third party computer system; a frequency regularization module adapted to group the plurality of batch jobs into at least one run frequency that includes at least one batch job; a load initialization module adapted to compute a load generated by each batch job in a first run frequency on the third party computer system based on each batch job's start time to protect against a worst case in which a number of batch operations in such given time period is higher than an average number of batch operations expected during the busiest of such given time period; and a start time determination module adapted to determine an optimized start time for each batch job in the first run frequency that meets the one or more constraints and that distributes each batch job's load on the third party computer system using each batch job's computed load and the current load, the one or more constraints including at least one constraint of the service level agreement.
 8. The system of claim 7, further comprising a time initialization module for initializing each batch job's start time to a preset value.
 9. The system of claim 7, wherein the frequency regularization module further adapted to regularize at least one batch job with an irregular run frequency from the plurality of batch jobs to a batch job with a regular frequency.
 10. The system of claim 7, further comprising a schedule generation module adapted to generate a batch job schedule for the first run frequency.
 11. The system of claim 7, further comprising a load update module adapted to update the current load on the computer system with loads of each batch job in the first frequency.
 12. The system of claim 11, wherein the load initialization module is further adapted to compute a load generated by each batch job in a second run frequency on the computer system based on each batch job's start time; and wherein the start time determination module is further adapted to determine an optimized start time for each batch job in the second run frequency that meets the one or more constraints and that distributes each batch job's load on the computer system using each batch job's computed load and the updated current load for the first run frequency.
 13. A machine-readable storage medium including a set of instructions to schedule execution of a plurality of batch jobs by a computer system, the instructions, when executed by a processor cause the machine to: read one or more constraints that constrain the execution of the plurality of batch jobs by the computer system, including constraints from a service level agreement, and a current load on the computer system; group the plurality of batch jobs into at least one run frequency that includes at least one batch job; set the at least one run frequency to a first run frequency; compute a load generated by each batch job in the first run frequency on the computer system based on each batch job's start time to protect against a worst case in which a number of batch operations in such given time period is higher than an average number of batch operations expected during the busiest of such given time period; and determine an optimized start time for each batch job in the first run frequency that meets the one or more constraints and that distributes each batch job's load on the computer system using each batch job's computed load and the current load, the one or more constraints including at least one constraint of the service level agreement.
 14. The machine-readable storage medium of claim 13, wherein the instructions cause the machine to initialize each batch job's start time to a preset value.
 15. The machine-readable storage medium of claim 13, wherein the instructions cause the machine to regularize at least one batch job with an irregular run frequency from the plurality of batch jobs to a batch job with a regular frequency.
 16. The machine-readable storage medium of claim 13, wherein the instructions cause the machine to generate a batch job schedule for the first run frequency.
 17. The machine-readable storage medium of claim 13, wherein the instructions cause the machine to update the current load on the computer system with loads of each batch job in the first frequency.
 18. The machine-readable storage medium of claim 17, wherein the instructions cause the machine to: set the at least one run frequency to a second run frequency; compute a load generated by each batch job in the second run frequency on the computer system based on each batch job's start time; and determine an optimized start time fir each batch job in the second run frequency that meets the one or more constraints and that distributes each batch job's load on the computer system using each batch job's computed load and the updated current load for the first run frequency. 